Ill suited to openhands
This model boasts good numbers, but the openhands integration isn't very good. I see looping issues, issues with tool calling, and it will never view the entire contents of a file no matter how much I prompt it to. It self limits to about 30 lines maximum which leads to tens of that file, tens of this file, and it's repeating endlessly. I tried to do some CSS+Python stuff 2.5 pro can do with the right context, it was pretty bad. It struggled to do anything. It fixed after viewing errors, but most of the time was just trying to access and move files.
I've had a similar experience, albeit not as bad. Dextral can code using open hands that's for sure. But it can't take in new information very well
Dextral works quite a bit better with Cursor and such
Hi everyone! How are you using Devstral? Local deployments? API?
I use it through a local deployment using a 4090 (llama.cpp server). I've tried q4_K_M and q5_K_M. So far I've found q4_K_M to be best because I can use a longer context size.
I will say, if the problem is something Dextral has seen before, it can definitely code it up. But if the API has changed in any way it really struggles even with hints and code snippets. I often see infinite loops of changing property names (e.g. back and forth between "spacing" and "space" but both being wrong). This makes using popular packages kind of cumbersome if a new version is released.
However, this could be user error on my part and may be easily solved with a memory-MCP, so I'll try that later.